Support Qureg.__int__ for multiple bits (little-endian) #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think this is the natural thing to do when asking for the
int
in a quregister. (Existing tests weren't changed because they happened to not check for this.)A reasonable follow-up change would be to remove the len==1 constraint from
__bool__
and__non_zero__
, and have them check if__int__
is non-zero instead. I can do that in this PR if you want.